SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Software appliance</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Software appliance</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">This article is about a software with just enough operating system (JeOS) to run on hardware or in a virtual machine. For a hardware device with integrated software (<a href="Firmware#Computers" title="Firmware">firmware</a>), see <a href="Computer_appliance" title="Computer appliance">computer appliance</a>.</div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1248332772">

/* start https://en.wikipedia.org/ */

.mw-parser-output .multiple-issues-text{width:95%;margin:0.2em 0}.mw-parser-output .multiple-issues-text>.mw-collapsible-content{margin-top:0.3em}.mw-parser-output .compact-ambox .ambox{border:none;border-collapse:collapse;background-color:transparent;margin:0 0 0 1.6em!important;padding:0!important;width:auto;display:block}body.mediawiki .mw-parser-output .compact-ambox .ambox.mbox-small-left{font-size:100%;width:auto;margin:0}.mw-parser-output .compact-ambox .ambox .mbox-text{padding:0!important;margin:0!important}.mw-parser-output .compact-ambox .ambox .mbox-text-span{display:list-item;line-height:1.5em;list-style-type:disc}body.skin-minerva .mw-parser-output .multiple-issues-text>.mw-collapsible-toggle,.mw-parser-output .compact-ambox .ambox .mbox-image,.mw-parser-output .compact-ambox .ambox .mbox-imageright,.mw-parser-output .compact-ambox .ambox .mbox-empty-cell,.mw-parser-output .compact-ambox .hide-when-compact{display:none}

/* end https://en.wikipedia.org/ */

</style>

<p>A <b>software appliance</b> is a <a href="Application_software" title="Application software">software application</a> combined with <a href="Just_enough_operating_system" title="Just enough operating system">just enough operating system (JeOS)</a> to run optimally on industry-standard hardware (typically a <a href="Server_(computing)#Hardware" title="Server (computing)">server</a>) or in a <a href="Virtual_machine" title="Virtual machine">virtual machine</a>.<sup id="cite_ref-Congdon,_Red_Hat_Blog,_2008_1-0" class="reference"><a href="#cite_note-Congdon,_Red_Hat_Blog,_2008-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> It is a <a href="Software_distribution" title="Software distribution">software distribution</a> or <a href="Firmware#Computers" title="Firmware">firmware</a> that implements a <a href="Computer_appliance" title="Computer appliance">computer appliance</a>.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup>

</p><p><a href="Virtual_appliance" title="Virtual appliance">Virtual appliances</a> are a subset of software appliances. The main distinction is the packaging format and the specificity of the target platform. A virtual appliance is a <a href="Virtual_machine_image" class="mw-redirect" title="Virtual machine image">virtual machine image</a> designed to run on a specific <a href="Platform_virtualization" class="mw-redirect" title="Platform virtualization">virtualization platform</a>, while a software appliance is often packaged in more generally applicable image format (e.g., <a href="Live_CD" title="Live CD">Live CD</a>) that supports installations to physical machines and multiple types of virtual machines.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>

</p><p>Installing a software appliance to a virtual machine and packaging that into an image, creates a virtual appliance.

</p>

<div class="mw-heading mw-heading2"><h2 id="Benefits">Benefits</h2></div>

<p>Software appliances have several benefits over traditional software applications that are installed on top of an <a href="Operating_system" title="Operating system">operating system</a>:

</p>

<ul><li>Simplified deployment: A software appliance encapsulates an application's dependencies in a pre-integrated, self-contained unit. This can dramatically simplify software deployment by freeing users from having to worry about resolving <a href="Dependency_hell" title="Dependency hell">potentially complex</a> OS compatibility issues, library dependencies or undesirable interactions with other applications. This is known as a "toaster."</li>

<li>Improved isolation: software appliances are typically used to run applications in isolation from one another. If the security of an appliance is compromised, or if the appliance crashes, other isolated appliances will not be affected.</li>

<li>Improved performance: A software appliance does not embed any unused operating system services, applications or any form of <a href="Software_bloat#Bloatware" title="Software bloat">bloatware</a> hence it does not have to share the hardware resources (CPU, memory, storage space, ...) usually consumed by these on a generic OS setup. This naturally leads to faster boot time and application execution speed. In the case where multiple software appliances share and run simultaneously on the same hardware (on a virtualization platform for example) this will not hold true as running <code>n</code> instances of a software appliance (OS + software application) will consume more hardware resources than running <code>n</code> instances of a software application on <code>1</code> instance of an operating system due to the overhead of running <code>n - 1</code> more instances of operating system.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Types_of_software_appliances">Types of software appliances</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Virtual_appliance">Virtual appliance</h3></div>

<p>A software appliance can be packaged in a <a href="Virtual_machine" title="Virtual machine">virtual machine</a> format as a <a href="Virtual_appliance" title="Virtual appliance">virtual appliance</a>, allowing it to be run within a virtual machine container.

</p><p>A virtual appliance could be built using either a standard virtual machine format such as <a href="Open_Virtualization_Format" title="Open Virtualization Format">Open Virtualization Format (OVF)</a>, or a format specific to a particular virtual machine container (for example, VMware, VirtualBox, or Amazon EC2).

</p>

<div class="mw-heading mw-heading3"><h3 id="Containers">Containers</h3></div>

<p><a href="Container_(virtualization)" class="mw-redirect" title="Container (virtualization)">Containers</a> and their images (such as those provided by <a href="Docker_(software)" title="Docker (software)">Docker</a> and Docker Hub) can be seen as an implementation of software appliances.

</p>

<div class="mw-heading mw-heading3"><h3 id="Live_CD_appliance">Live CD appliance</h3></div>

<p>A software appliance can be packaged as a <a href="Live_CD" title="Live CD">Live CD</a> image, allowing it to run on real hardware in addition to most types of virtual machines.

</p><p>This allows developers to avoid the complexities involved in supporting multiple incompatible virtual machine image formats and focus on the lowest common denominator instead (i.e., ISO images are supported by most Virtual Machine platforms).

</p>

<div class="mw-heading mw-heading2"><h2 id="Commercial_software_appliances">Commercial software appliances</h2></div>

<p>Commercial software appliances are typically sold as a subscription service

(pay-as-you-go) and are an alternative approach to <a href="Software_as_a_service" title="Software as a service">software as a service</a>.

</p><p>Customers can receive all service and maintenance from the application vendor, eliminating the requirement to manage multiple maintenance streams, licenses, and service contracts.

</p><p>In some cases, the application vendor may install the software appliance on a piece of hardware prior to delivery to the customer, thereby creating a <a href="Computer_appliance" title="Computer appliance">computer appliance</a>. In both cases, the primary value to the customer remains the simplicity of purchase, deployment, and maintenance.

</p>

<ul><li><a href="Portable_application" title="Portable application">Portable application</a></li>

<li><a href="Virtual_appliance" title="Virtual appliance">Virtual appliance</a></li>

<li><a href="BitNami" class="mw-redirect" title="BitNami">BitNami</a></li>

<li><a href="TurnKey_Linux_Virtual_Appliance_Library" title="TurnKey Linux Virtual Appliance Library">TurnKey Linux Virtual Appliance Library</a></li>

<li><a href="SUSE_Studio" title="SUSE Studio">SUSE Studio</a> - builds software appliances</li>

<li><a href="Windows_To_Go" title="Windows To Go">Windows To Go</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFCongdon2008" class="citation web cs1">Congdon, Lee (25 January 2008). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190715204511/https://www.redhat.com/en/blog/what-is-a-software-appliance">"What is a Software Appliance?"</a>. <i><a href="Red_Hat" title="Red Hat">Red Hat Blog</a></i>. Archived from <a rel="nofollow" class="external text" href="https://www.redhat.com/en/blog/what-is-a-software-appliance">the original</a> on 15 July 2019<span class="reference-accessdate">. Retrieved <span class="nowrap">29 December</span> 2019</span>.</cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite id="CITEREFSmith,_BobHardin,_John_APhillips,_GrahamPierce,_Bill2007" class="citation book cs1">Smith, Bob; Hardin, John A; Phillips, Graham; Pierce, Bill (2007). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=uVu0ax6C3uIC&q=%22network+appliance%22+date:2003-2009&pg=PA81"><i>Linux Appliance Design: A Hands-On Guide to Building Linux Appliances</i></a>. No Starch Press. pp. xvii. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-59327-140-4</bdi><span class="reference-accessdate">. Retrieved <span class="nowrap">2008-05-06</span></span>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><i><a rel="nofollow" class="external text" href="http://www.networkworld.com/topics/sans.html">SAN Data Center</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20050502092915/http://www.networkworld.com/topics/sans.html">Archived</a> 2005-05-02 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></i>- Network World</span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.dmtf.org/standards/published_documents/DSP0243_1.1.0.pdf">"OVF 1.1 Specification"</a> <span class="cs1-format">(PDF)</span>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.virtualbox.org/wiki/Changelog">"VirtualBox changelog"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2009-04-13</span></span>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text">Wu C F, Wang Y S, Liu G N, Amies, A, 2012, <a rel="nofollow" class="external text" href="http://www.ibm.com/developerworks/cloud/library/cl-smartcloudsolution2/index.html">Create solutions on IBM SmartCloud Enterprise: Transfer image assets between different accounts</a> <i>IBM developerWorks</i>, June 6.</span>

</li>

</ol></div></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-12-09" href="https://en.wikipedia.org/wiki/?title=Software_appliance&oldid=1262066844">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>